Transferring digital receipt data to mobile devices

ABSTRACT

The present invention extends to methods, systems, and computer program products f0r transferring digital receipt data to mobile devices. A point-of-sale (“POS”) system generates digital receipt data as part of a sales transaction. The point-of-sale (“POS”) system and a mobile device, possibly also along with a receipt data server, interoperate with one another to transfer digital receipt data generated to the mobile device. In some embodiments, the point-of-sale (“POS”) system transfers digital receipt data for a sales transaction to the receipt data server. An identifier, such as, for example, an application identifier or transaction identifier, is stored along with the digital receipt data to match the digital receipt data with the mobile device. The mobile device subsequently uses the identifier to access the digital receipt data from the receipt data server. In other embodiments, the point-of-sale (“POS”) system transfers digital receipt data directly to the mobile device.

RELATED APPLICATIONS

This application is related to U.S. application Ser. No. 13/556,024,filed Jul. 23, 2012 and U.S. zaapplication Ser. No. 13/556,056, filedJul. 23, 2012.

BACKGROUND

1. Field of the Invention

This invention relates generally to the field of electronic salestransactions, and, more particularly, to transferring digital receiptsto mobile devices.

2. Related Art

In a variety of transactions, consumers or buyers of goods or servicestypically receive receipts from their respective merchants or serviceproviders as proof of existence of conducted transactions. Generally,receipts are issued by merchants and service providers for a number ofreasons including, for example, regulatory or tax reasons andconvenience purposes. A receipt provides information about acorresponding transaction for the purpose of providing all participantswith a trace or record of the transaction. Receipts can later be used bya consumer for various purposes including, for example, provingparticipation in a transaction for tax reporting purpose, productreturns, use as a claim ticket for a further transaction, provisioningwarranties, etc. For in-store purchases, consumers generally obtain apaper receipt at the point-of-sale. Accordingly, consumers frequentlyretain paper receipts for some amount of time after a transaction. Savedpaper receipts can then be used by consumers later to returnmerchandise, to track expenses for budgeting purposes, or tosubstantiate tax, reimbursement, or warranty claims, among many otheruses.

However, these later uses may be distant in time relative to when atransaction occurred. Weeks, months, or even years may pass before aconsumer needs to use an old paper receipt. For example, one consumermay need to submit all receipts associated with business expenses to anemployer at the end of a month for reimbursement purposes. Anotherconsumer may need to submit all receipts related to charitablecontributions to her accountant at the end of the tax year for incomededuction purposes. In either of these instances, or the countless otherinstances in which a consumer has a need to retrieve old paper receipts,the consumer must rely on their past diligence in storing and organizingthe paper receipts (and making sure the paper receipts do not becomeworn or damaged) in order to achieve her intended goal. For the averageconsumer, it is a time-consuming endeavor to locate the particular paperreceipt(s) needed, and it may in fact prove to be impossible. Paperreceipts are easily misplaced and difficult to organize—not only do theycome in all different shapes and sizes, but they may only be categorizedat the highest level in one manner, for example, by date or by subjectmatter.

Indeed, the high-level categorization initially chosen fororganizational purposes may not be altered without a great deal of work,which is problematic when a particular paper receipt would be locatedmost easily through a category other than the one chosen. As such,typically methods of saving paper receipts have at least a number oflimitations. At best, these limitations cost consumers their time andsanity as they wade through old receipts to find what they need; atworst, they cost consumers much more—the inability to obtain a refund, atax deduction, a reimbursement, etc.

Although receipts for telephone or online purchases may be delivered toa customer in digital format, this does not relieve, and in someenvironments may compound, organizational difficulties associated withpaper receipts. For example, for telephone or online purchases,consumers may wait for a paper receipt to arrive in the mail, or mayobtain an electronic receipt that they print to generate a paperreceipt. These paper receipts must then be retained and organized withother paper receipts. Further, some consumers may never print theelectronic receipts they obtain, and instead retain those receipts inelectronic form, for example, in their email accounts. As such,consumers may store old receipts in one or more locations, both physicaland electronic, and the stored receipts are only as organized as theparticular consumer's efforts dictate.

Another drawback to the use of paper receipts is that, unlikecredit/debit transactions, individual cash transactions are not storedin conventional point-of-sale (“POS”) systems. Customers can read theirown credit/debit transaction data at the websites of their banks orcredit card companies. However, since the cash transactions are notstored, the paper receipts are the only record of these cashtransactions.

A conventional POS system typically includes a POS terminal, one or moreperipheral devices (display monitor, receipt printer, barcode scanner,weigh scale, electronic signature pad) and a payment processor with pinpad (for credit and debit cards). The data for sales transactions isusually stored in a storage device of the POS terminal, which may beuploaded to one of the remote transaction authorization server oranother remote server of the credit/debit card companies. Although POSsystems are well equipped for merchants to monitor and collecttransaction data from the POS system, the ability of the customer toinput or extract useful information from the POS system is typicallylimited to pinpad interactions (entering tip amounts, obtainingadditional cash back, etc.), and obtaining printed receipts, the formatand content of which has been pre-determined by the merchant.

Further, POS systems are typically sold with a proprietary on-boardsoftware system that may be specific to the merchant's business. Themerchant is able to make minor programming adjustments to add discountcodes and other special offers, but has limited ability to addfunctionality to the POS system.

BRIEF DESCRIPTION OF THE DRAWINGS

The specific features, aspects and advantages of the present inventionwill become better understood with regard to the following descriptionand accompanying drawings where:

FIG. 1 illustrates an example block diagram of a computing device.

FIG. 2 illustrates an example computer architecture that facilitatestransferring digital receipt data to mobile devices.

FIGS. 3A and 3B illustrates a flow chart of an example method fortransferring digital receipt data to mobile devices.

FIG. 4 illustrates another example computer architecture thatfacilitates transferring digital receipt data to mobile devices.

FIGS. 5A and 5B illustrates another flow chart of an example method fortransferring digital receipt data to mobile devices.

FIG. 6 illustrates a further example computer architecture thatfacilitates transferring digital receipt data to mobile devices.

FIG. 7 illustrates further flow chart of an example method fortransferring digital receipt data to mobile devices.

FIG. 8 illustrates an example schematic block diagram of a point-of-sale(“POS”) system.

FIG. 9 illustrates an example schematic block diagram of a network ofpoint-of-sale (“POS”) systems.

DETAILED DESCRIPTION

The present invention extends to methods, systems, and computer programproducts for transferring digital receipt data to mobile devices. In thefollowing description of the present invention, reference is made to theaccompanying drawings, which form a part hereof, and in which is shownby way of illustration specific embodiments in which the invention ismay be practiced. It is understood that other embodiments may beutilized and structural changes may be made without departing from thescope of the present invention.

Embodiments of the present invention may comprise or utilize a specialpurpose or general-purpose computer including computer hardware, suchas, for example, one or more processors and system memory, as discussedin greater detail below. Embodiments within the scope of the presentinvention also include physical and other computer-readable media forcarrying or storing computer-executable instructions and/or datastructures. Such computer-readable media can be any available media thatcan be accessed by a general purpose or special purpose computer system.Computer-readable media that store computer-executable instructions arecomputer storage media (devices). Computer-readable media that carrycomputer-executable instructions are transmission media. Thus, by way ofexample, and not limitation, embodiments of the invention can compriseat least two distinctly different kinds of computer-readable media:computer storage media (devices) and transmission media.

Computer storage media (devices) includes RAM, ROM, EEPROM, CD-ROM,solid state drives (“SSDs”) (e.g., based on RAM), Flash memory,phase-change memory (“PCM”), other types of memory, other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium which can be used to store desired program code means inthe form of computer-executable instructions or data structures andwhich can be accessed by a general purpose or special purpose computer.

A “network” is defined as one or more data links that enable thetransport of electronic data between computer systems and/or modulesand/or other electronic devices. When information is transferred orprovided over a network or another communications connection (eitherhardwired, wireless, or a combination of hardwired or wireless) to acomputer, the computer properly views the connection as a transmissionmedium. Transmissions media can include a network and/or data linkswhich can be used to carry desired program code means in the form ofcomputer-executable instructions or data structures and which can beaccessed by a general purpose or special purpose computer. Combinationsof the above should also be included within the scope ofcomputer-readable media.

Further, upon reaching various computer system components, program codemeans in the form of computer-executable instructions or data structurescan be transferred automatically from transmission media to computerstorage media (devices) (or vice versa). For example,computer-executable instructions or data structures received over anetwork or data link can be buffered in RAM within a network interfacemodule (e.g., a “NIC”), and then eventually transferred to computersystem RAM and/or to less volatile computer storage media (devices) at acomputer system. RAM can also include solid state drives (SSDs or PCIxbased real time memory tiered Storage, such as FusionIO). Thus, itshould be understood that computer storage media (devices) can beincluded in computer system components that also (or even primarily)utilize transmission media.

Computer-executable instructions comprise, for example, instructions anddata which, when executed at a processor, cause a general purposecomputer, special purpose computer, or special purpose processing deviceto perform a certain function or group of functions. The computerexecutable instructions may be, for example, binaries, intermediateformat instructions such as assembly language, or even source code.Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the described features or acts described above.Rather, the described features and acts are disclosed as example formsof implementing the claims.

Those skilled in the art will appreciate that the invention may bepracticed in network computing environments with many types of computersystem configurations, including, personal computers, desktop computers,laptop computers, message processors, hand-held devices, multi-processorsystems, microprocessor-based or programmable consumer electronics,network PCs, minicomputers, mainframe computers, mobile telephones,PDAs, tablets, pagers, routers, switches, various storage devices, andthe like. The invention may also be practiced in distributed systemenvironments where local and remote computer systems, which are linked(either by hardwired data links, wireless data links, or by acombination of hardwired and wireless data links) through a network,both perform tasks. In a distributed system environment, program modulesmay be located in both local and remote memory storage devices.

Embodiments of the invention can also be implemented in cloud computingenvironments. In this description and the following claims, “cloudcomputing” is defined as a model for enabling ubiquitous, convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, servers, storage, applications, and services)that can be rapidly provisioned via virtualization and released withminimal management effort or service provider interaction, and thenscaled accordingly. A cloud model can be composed of variouscharacteristics (e.g., on-demand self-service, broad network access,resource pooling, rapid elasticity, measured service, etc.), servicemodels (e.g., Software as a Service (“SaaS”), Platform as a Service(“PaaS”), Infrastructure as a Service (“IaaS”), and deployment models(e.g., private cloud, community cloud, public cloud, hybrid cloud,etc.).

It is further noted that, where feasible, functions described herein canbe performed in one or more of: hardware, software, firmware, digitalcomponents, or analog components. For example, one or more applicationspecific integrated circuits (“ASICs”) can be programmed to carry outone or more of the systems and procedures described herein. Certainterms are used throughout the following description and Claims to referto particular system components. As one skilled in the art willappreciate, components may be referred to by different names. Thisdocument does not intend to distinguish between components that differin name, but not function

In general, embodiments of the invention are directed to transferringdigital receipt data to mobile devices. A point-of-sale (“POS”) systemgenerates digital receipt data as part of a sales transaction. Thepoint-of-sale (“POS”) system and a mobile device, possibly also alongwith a receipt data server, interoperate with one another to transferdigital receipt data generated to the mobile device.

In some embodiments, the point-of-sale (“POS”) system transfers digitalreceipt data for a sales transaction to the receipt data server. Anidentifier, such as, for example, an application identifier ortransaction identifier, is stored along with the digital receipt data tomatch the digital receipt data with the mobile device. The mobile devicesubsequently uses the identifier to access the digital receipt data fromthe receipt data server. In other embodiments, the point-of-sale (“POS”)system transfers digital receipt data directly to the mobile device.

FIG. 1 illustrates an example block diagram of a computing device 100.Computing device 100 can be used to perform various procedures, such asthose discussed herein. Computing device 100 can function as a server, aclient, or any other computing entity. Computing device 100 can performvarious communication and data transfer functions as described hereinand can execute one or more application programs, such as theapplication programs described herein. Computing device 100 can be anyof a wide variety of computing devices, such as a mobile telephone orother mobile device, a desktop computer, a notebook computer, a servercomputer, a handheld computer, tablet computer and the like.

Computing device 100 includes one or more processor(s) 102, one or morememory device(s) 104, one or more interface(s) 106, one or more massstorage device(s) 108, one or more Input/Output (I/O) device(s) 110, anda display device 130 all of which are coupled to a bus 112. Processor(s)102 include one or more processors or controllers that executeinstructions stored in memory device(s) 104 and/or mass storagedevice(s) 108. Processor(s) 102 may also include various types ofcomputer-readable media, such as cache memory.

Memory device(s) 104 include various computer-readable media, such asvolatile memory (e.g., random access memory (“RAM”) 114) and/ornonvolatile memory (e.g., read-only memory (“ROM”) 116). Memorydevice(s) 104 may also include rewritable ROM, such as Flash memory.

Mass storage device(s) 108 include various computer readable media, suchas magnetic tapes, magnetic disks, optical disks, solid state memory(e.g., Flash memory), and so forth. As shown in FIG. 1, a particularmass storage device is a hard disk drive 124. Various drives may also beincluded in mass storage device(s) 108 to enable reading from and/orwriting to the various computer readable media. Mass storage device(s)108 include removable media 126 and/or non-removable media.

I/O device(s) 110 include various devices that allow data and/or otherinformation to be input to or retrieved from computing device 100.Example I/O device(s) 110 include cursor control devices, keyboards,keypads, microphones, monitors or other display devices, speakers,printers, network interface cards, modems, cameras, lenses, CCDs orother image capture devices, and the like.

Display device 130 includes any type of device capable of displayinginformation to one or more users of computing device 100. Examples ofdisplay device 130 include a monitor, display terminal, video projectiondevice, and the like.

Interface(s) 106 include various interfaces that allow computing device100 to interact with other systems, devices, or computing environments.Example interface(s) 106 can include any number of different networkinterfaces 120, such as interfaces to personal area networks (“PANs”),local area networks (“LANs”), wide area networks (“WANs”), wirelessnetworks (e.g., near field communication (“NFC”), Bluetooth, Wi-Fi, etc.networks), and the Internet. Other interfaces include user interface 118and peripheral device interface 122.

Bus 112 allows processor(s) 102, memory device(s) 104, interface(s) 106,mass storage device(s) 108, and I/O device(s) 110 to communicate withone another, as well as other devices or components coupled to bus 112.Bus 112 represents one or more of several types of bus structures, suchas a system bus, PCI bus, IEEE 1394 bus, USB bus, and so forth.

FIG. 2 illustrates an example computer architecture 200 that facilitatestransferring digital receipt data to mobile devices. Referring to FIG.2, computer architecture 200 includes mobile device 201, POS system 211,and receipt data server 221. Each of the depicted components can beconnected to one another over (or be part of) a network, such as, forexample, a PAN, a LAN, a WAN, and even the Internet. Accordingly, eachof the depicted components as well as any other connected computersystems and their components, can create message related data andexchange message related data (e.g., near field communication (“NFC”)payloads, Bluetooth packets, Internet Protocol (“IP”) datagrams andother higher layer protocols that utilize IP datagrams, such as,Transmission Control Protocol (“TCP”), Hypertext Transfer Protocol(“HTTP”), Simple Mail Transfer Protocol (“SMTP”), etc.) over thenetwork.

As depicted, mobile device 201 (e.g., a smartphone) further includesreceipt management application 202, network adapter 203, and NFC module204. Generally, receipt management application 202 is configured tomanage receipt data for a user of mobile device 201. Receipt managementapplication 202 can be used to perform receipt related operations, suchas, for example, sorting receipt data, searching receipt data, itemizingreceipt data, etc. in response to user-entered commands. Receiptmanagement application 202 is also associated with application ID 231.Application ID 231 can be a unique ID used to distinguish receiptmanagement application 202 (and thus also mobile device 201) from otherreceipt management applications (and thus also from other mobiledevices).

Network adapter 203 can be a wireless network adapter for connectingmobile device 201 with a wireless network, such as, for example, Wi-Fiand/or a cellular network (e.g., CDMA, GSM, iDen, etc.) that facilitatesa further connection to network 251 (e.g., the Internet). NFC module 204is configured to connect mobile device 201 with other systems anddevices using Near Field Communication.

As depicted, POS system 211 includes transaction processor 212, networkadapter 213, NFC module 214, and I/O peripherals 216. POS 211 can bephysically located at a checkout lane in a store. Generally, transactionprocessor 212 is configured to manage sales transactions for POS system211. Transaction processor 212 can receive input from I/O peripherals216 to open a sales transaction, collect digital receipt data (e.g.,date, time, item, and cost data, etc.) for a sales transaction, andclose a sales transaction. Digital receipt data for an item (e.g. itemdescription and item cost) can be retrieved from an item database inresponse to scanning a barcode on (or otherwise identifying) the item.I/O peripherals 216 can include one or more of: a monitor (e.g., acashier-facing monitor), one or more input devices (e.g., scanners,keyboards, scales, or the like), one or more payment devices (e.g., cashdrawers, card readers, etc.) for receiving or returning payments, andone or more output devices (e.g., customer-facing display or monitor,receipt printer, etc.).

Network adapter 213 can be a wired or wireless network adapter forconnecting POS system 211 with a network, such as, for example, a Wi-Fiand/or wired Ethernet network, that facilitates a further connection tonetwork 251 (e.g., the Internet). NFC module 214 is configured toconnect POS system 211 with other systems and devices using Near FieldCommunication.

Generally, receipt data server 221 is configured to receive and storereceipt data from POS system 211 (and possibly also one or more otherPOS systems). Receipt data server 221 is also connected to network 251.In some embodiments, receipt data server 221 is part of a backend systemthat receives receipt data from a plurality of POS systems distributedthroughout different geographic locations. The plurality of POS systemsand the backend system can be part of a commonly owned and/or controlledcorporate network infrastructure.

FIGS. 3A and 3B illustrate a flow chart 300 of an example method fortransferring digital receipt data to mobile devices. Method 300 will bedescribed with respect to the components and data of computerarchitecture 200.

Method 300 includes opening a sales transaction associated with a mobiledevice (301). A user of mobile device 201 can make one or more itemsthey wish to purchase available to a cashier. The cashier can thenprocess (e.g., scan) each of the items as part of a checkout procedure.Alternately, the user of mobile device 201 can process (e.g., scan) eachof the one or more items himself or herself as part of a self-checkoutprocedure. As part of the checkout process, a cashier or the user ofmobile device 201 can enter commands at I/O peripherals 216 to start anew sales transaction. In response, I/O peripherals 216 can send opentransaction message 232 to transaction processor 212. Transactionprocessor 212 can receive open transaction message 232 from I/Operipherals 216. In response to open transaction message 232,transaction processor 212 can open a sales transaction to process theone or more items for the user of mobile device 201.

Method 300 includes in response to opening the sales transaction,collecting digital receipt data for the sales transaction (302). Forexample, in response to opening the sales transaction, transactionprocessor 212 can collect digital receipt data 233 for each of the oneor more items that is processed (e.g., scanned) during the salestransaction.

Method 300 includes transmitting a Near Field Communication (NFC) tagpayload within a Radio Frequency (RF) field range of the point-of-sale(POS) system, the Near Field Communication (NFC) tag payload encoding aunique customer identifier, the unique customer identifier correspondingto a receipt management application resident at the mobile device (303).For example, NFC module 204 can access application ID 231 from receiptmanagement application 202. NFC module 204 can transmit NFC tag payload238 within a RF field range of POS system 211. NFC tag payload 238encodes application ID 231, a unique ID for receipt managementapplication 202.

Method 300 includes receiving the Near Field Communication (NFC) tagpayload from the mobile device (304). For example, NFC module 214 canreceive NFC tag payload 238 from NFC module 204. NFC module 214 candecode application ID 231 from NFC tag payload 238 and send applicationID 231 to transaction processor 212.

In these embodiments, mobile device 201 can function as an NFC tag andPOS system 211 can function as an NFC reader. Mobile device 201 can bemoved within a sufficient proximity of POS system 211 so that POS system211 can receive NFC tag payload 238.

Method 300 includes closing the sales transaction (305). For example,when each of the one or more items has been processed (e.g., scanned), acashier or the user of mobile device 201 can enter commands at I/Operipherals 216 to end the sales transaction. In response, I/Operipherals 216 can send close transaction message 234 to transactionprocessor 212. Transaction processor 212 can receive close transactionmessage 234 from I/O peripherals 216. In response to close transactionmessage 234, transaction processor 212 can close the sales transactionprocessing the one or more items for the user of mobile device 201.

Method 300 includes, in response to closing the sales transaction, usingthe unique customer identifier to mark the digital receipt data for thesales transaction as corresponding to the receipt management application(306). For example, transaction processor 212 can use application ID 231to mark digital receipt data 233 as corresponding to receipt managementapplication 202.

Method 300 includes, also in response to closing the sales transaction,sending the marked digital receipt data for the sales transaction to areceipt data server for subsequent retrieval by the mobile device (307).For example, network adapter 213 can access digital receipt data 233marked with application ID 231 from transaction processor 212. Networkadapter 213 can send digital receipt data 233 marked with application ID231 to receipt data server 221.

Receipt data server can store digital receipt data 233 and retain themarking with application ID 231.

Method 300 includes receiving a push notification, the push notificationnotifying the mobile device that digital receipt data for the salestransaction is available at the receipt data server (308). For example,receipt data server 221 can send push notification 237 to mobile device201. Alternately, POS system 211 can send push notification 237 tomobile device 201. Mobile device 201 can receive push notification 237from receipt data server 221 (or alternately from POS system 211). Pushnotification 237 notifies mobile device 201 that digital receipt data233 is available at receipt data server 221.

Method 300 includes requesting digital receipt data corresponding to theunique customer identifier from the receipt data server (309). Forexample, network adapter 203 can send request 239, containingapplication ID 231, to receipt data server 221. Request 239 requests anydigital receipt data for receipt management application 202. Receiptdata server 221 can receive request 239. Receipt data server 221 can useapplication ID 231 to match request 239 to digital receipt data 233.Receipt data server 221 can return digital receipt data 233 to mobiledevice 201.

Method 300 includes receiving the digital receipt data for the salestransaction from the receipt data server in response to the request(310). For example, network adapter 203 can receive digital receipt data233 from data receipt data server 221. Method 300 includes deliveringthe electronic receipt data for the sales transaction to the receiptmanagement application (act 311). For example, network adapter 203 candeliver digital receipt data 233 to receipt management application 202.Receipt management application 202 can then process digital receipt data233 to sort digital receipt data 233, search digital receipt data 233,itemize digital receipt data 233, etc. in response to user-enteredcommands.

FIG. 4 illustrates an example computer architecture 400 that facilitatestransferring digital receipt data to mobile devices. Referring to FIG.4, computer architecture 400 includes mobile device 401, POS system 411,and receipt data server 421. Each of the depicted components can beconnected to one another over (or be part of) a network, such as, forexample, a PAN, a LAN, a WAN, and even the Internet. Accordingly, eachof the depicted components as well as any other connected computersystems and their components, can create message related data andexchange message related data (e.g., near field communication (“NFC”)payloads, Bluetooth packets, Internet Protocol (“IP”) datagrams andother higher layer protocols that utilize IP datagrams, such as,Transmission Control Protocol (“TCP”), Hypertext Transfer Protocol(“HTTP”), Simple Mail Transfer Protocol (“SMTP”), etc.) over thenetwork.

As depicted, mobile device 401 (e.g., a smartphone) further includesreceipt management application 402, network adapter 403, and NFC module404. Generally, receipt management application 402 is configured tomanage receipt data for a user of mobile device 401. Receipt managementapplication 402 can be used to perform receipt related operations, suchas, for example, sorting receipt data, searching receipt data, itemizingreceipt data, etc. in response to user-entered commands. However,receipt management application 402 is not associated with a unique ID.As such, receipt management application 402 may be incapable of uniqueidentification relative to other receipt management applicationsinteracting with POS system 411 or requesting digital receipt data fromreceipt data server 421.

Network adapter 403 can be a wireless network adapter for connectingmobile device 401 with a wireless network, such as, for example, Wi-Fiand/or a cellular network (e.g., CDMA, GSM, iDen, etc.) that facilitatesa further connection to network 451 (e.g., the Internet). NFC module 404is configured to connect mobile device 401 with other systems anddevices using Near Field Communication.

As depicted, POS system 411 includes transaction processor 412, networkadapter 413, NFC module 414, and I/O peripherals 416. POS 411 can bephysically located at a checkout lane in a store. Generally, transactionprocessor 412 is configured to manage sales transactions for POS 411.Transaction processor 412 can receive input from I/O peripherals 416 toopen a sales transaction, collect digital receipt data (e.g., date,time, item, and cost data, etc.) for a sales transaction, and close asales transaction. Digital receipt data for an item (e.g. itemdescription and item cost) can be retrieved from an item database inresponse to scanning a barcode on (or otherwise identifying) the item.I/O peripherals 416 can include one or more of: a monitor (e.g., acashier-facing monitor), one or more input devices (e.g., scanners,keyboards, scales, or the like), one or more payment devices (e.g., cashdrawers, card readers, etc.) for receiving or returning payments, andone or more output devices (e.g., customer-facing display or monitor,receipt printer, etc.).

Network adapter 413 can be a wired or wireless network adapter forconnecting mobile phone 401 with a network, such as, for example, aWi-Fi and/or wired Ethernet network, that facilitates a furtherconnection to network 451 (e.g., the Internet). NFC module 414 isconfigured to connect POS system 411 with other systems and devicesusing Near Field Communication.

Generally, receipt data server 421 is configured to receive and storereceipt data from POS system 411 (and possibly also one or more otherPOS systems). Receipt data server 421 is also connected to network 451.In some embodiments, receipt data server 421 is part of a backend systemthat receives receipt data from a plurality of POS systems distributedthroughout different geographic locations. The plurality of POS systemsand the backend system can be part of a commonly owned and/or controlledcorporate network infrastructure.

FIGS. 5A and 5B illustrate a flow chart of an example method 500 fortransferring digital receipt data to mobile devices. Method 500 will bedescribed with respect to the components and data of computerarchitecture 400.

Method 500 includes beginning a sales transaction associated with amobile device (501). A user of mobile device 401 can make one or moreitems they wish to purchase available to a cashier. The cashier can thenprocess (e.g., scan) each of the items as part of a checkout procedure.Alternately, the user of mobile device 401 can process (e.g., scan) eachof the one or more items himself or herself as part of a self-checkoutprocedure. As part of the checkout process, a cashier or the user ofmobile device 401 can enter commands at I/O peripherals 416 to start anew sales transaction. In response, I/O peripherals 416 can send opentransaction message 432 to transaction processor 412. Transactionprocessor 412 can receive open transaction message 432 from I/Operipherals 416. In response to open transaction message 432,transaction processor 412 can open a sales transaction to process theone or more items for the user of mobile device 401.

Method 500 includes, in response to opening the sales transaction,collecting digital receipt data for the sales transaction (502). Forexample, in response to opening the sales transaction, transactionprocessor 412 can collect digital receipt data 433 for each of the oneor more items that is processed (e.g., scanned) during the salestransaction.

Method 500 includes, also in response to opening the sales transaction,formulating a transaction identifier for the sales transaction (503).For example, in response to opening the sales transaction, transactionprocessor 412 can formulate transaction identifier 413 for the salestransaction. Transaction identifier 413 can be a unique transactionidentifier relative to other transactions occurring at POS system 411and to other transactions at other POS systems in communication withreceipt data server 421.

Method 500 includes, also in response to opening the sales transaction,transmitting a Near Field Communication (NFC) tag payload within a RadioFrequency (RF) field range of the mobile device, the Near FieldCommunication (NFC) tag payload encoding the transaction identifier forthe sales transaction (504). For example, in response to opening thesales transaction, NFC module 414 can access transaction ID 431 fromtransaction processor 412. NFC module 414 can transmit NFC tag payload438 within a RF field range of mobile device 401. NFC tag payload 438encodes transaction ID 431, a unique ID for the transaction.

Method 500 includes receiving the Near Field Communication (NFC) tagpayload from the point-of-sale (POS) system (505). For example, NFCmodule 404 can receive NFC tag payload 438 from NFC module 414. NFCmodule 404 can decode transaction ID 431 from NFC tag payload 438 andsend transaction ID 431 to receipt management application 402.

In these embodiments, mobile device 401 can function as an NFC readerand POS system 411 can function as an NFC tag. Mobile device 401 can bemoved within a sufficient proximity of POS system 411 so that mobiledevice 401 can receive NFC tag payload 438.

Method 500 includes closing the sales transaction at the point-of-sale(POS) system (506). For example, when each of the one or more items hasbeen processed (e.g., scanned), a cashier or the user of mobile device401 can enter commands at I/O peripherals 416 to end the salestransaction. In response, I/O peripherals 416 can send close transactionmessage 434 to transaction processor 412. Transaction processor 412 canreceive close transaction message 434 from I/O peripherals 416. Inresponse to close transaction message 434, transaction processor 412 canclose the sales transaction processing the one or more items for theuser of mobile device 401.

Method 500 includes, in response to closing the sales transaction, usingthe transaction identifier to mark the digital receipt data for thesales transaction (507). For example, transaction processor 412 can usetransaction ID 431 to mark digital receipt data 433 as corresponding tothe transaction with mobile device 401.

Method 500 includes, also in response to closing the sales transaction,sending the marked digital receipt data for the sales transaction to areceipt data server for subsequent retrieval by the mobile device (508).For example, network adapter 413 can access digital receipt data 433marked with transaction ID 431 from transaction processor 412. Networkadapter 413 can send digital receipt data 433 marked with transaction ID431 to receipt data server 421.

Method 500 includes receiving the push notification, the pushnotification notifying the mobile device that digital receipt data forthe sales transaction is available at the receipt data server (509). Forexample, receipt data server 421 can send push notification 437 tomobile device 401. Alternately, POS system 411 can send pushnotification 437 to mobile device 401. Mobile device 401 can receivepush notification 437 from receipt data server 421 (or alternately fromPOS system 411). Push notification 437 notifies mobile device 401 thatdigital receipt data 433 is available at receipt data server 421

Method 500 includes requesting digital receipt data corresponding to thetransaction identifier from the receipt data server (510). For example,network adapter 403 can send request 439, containing transaction ID 431,to receipt data server 421. Request 439 requests any digital receiptdata corresponding to the transaction associated with transaction ID431. Receipt data server 421 can receive request 439. Receipt dataserver 421 can use transaction ID 431 to match request 439 to digitalreceipt data 433. Receipt data server 421 can return digital receiptdata 433 to mobile device 401.

Method 500 includes receiving the digital receipt data for the salestransaction from the receipt data server in response to the request(511). For example, network adapter 403 can receive digital receipt data433 from data receipt data server 421. Method 500 includes deliveringthe electronic receipt data for the sales transaction to a receiptmanagement application at the mobile device (512). For example, networkadapter 403 can deliver digital receipt data 433 to receipt managementapplication 402. Receipt management application 402 can then processdigital receipt data 433 to sort digital receipt data 433, searchdigital receipt data 433, itemize digital receipt data 433, etc. inresponse to user-entered commands.

FIG. 6 illustrates an example computer architecture 600 that facilitatestransferring digital receipt data to mobile devices. Referring to FIG.6, computer architecture 600 includes mobile device 601 and POS system611. Each of the depicted components can be connected to one anotherover (or be part of) a network, such as, for example, a Personal AreaNetwork (“PAN”), a Local Area Network (“LAN”), a Wide Area Network(“WAN”), and even the Internet. Accordingly, each of the depictedcomponents as well as any other connected computer systems and theircomponents, can create message related data and exchange message relateddata (e.g., near field communication (NFC) payloads, Bluetooth packets,Internet Protocol (“IP”) datagrams and other higher layer protocols thatutilize IP datagrams, such as, Transmission Control Protocol (“TCP”),Hypertext Transfer Protocol (“HTTP”), Simple Mail Transfer Protocol(“SMTP”), etc.) over the network.

As depicted, mobile device 601 (e.g., a smartphone) further includesreceipt management application 602, communication module 603, and NFCmodule 604. Generally, receipt management application 602 is configuredto manage receipt data for a user of mobile device 601. Receiptmanagement application 602 can be used to perform receipt relatedoperations, such as, for example, sorting receipt data, searchingreceipt data, itemizing receipt data, etc. in response to user-enteredcommands. Receipt management application 602 is also associated withapplication ID 631. Application ID 631 can be a unique ID used todistinguish receipt management application 602 (and thus also mobiledevice 601) from other receipt management applications (and thus alsofrom other mobile devices).

Communication module 603 can be a wireless network adapter forconnecting mobile device 601 with a local wireless network, such as, forexample, using Bluetooth and/or Wi-Fi. NFC module 604 is configured toconnect mobile device 601 with other systems and devices using NearField Communication.

As depicted, POS system 611 includes transaction processor 612,communication module 613, NFC module 614, and I/O peripherals 616. POS611 can be physically located at a checkout lane in a store. Generally,transaction processor 612 is configured to manage sales transactions forPOS 611. Transaction processor 612 can receive input from I/Operipherals 616 to open a sales transaction, collect digital receiptdata (e.g., date, time, item, and cost data, etc.) for a salestransaction, and close a sales transaction. Digital receipt data for anitem (e.g. item description and item cost) can be retrieved from an itemdatabase in response to scanning a barcode on (or otherwise identifying)the item. I/O peripherals 616 can include one or more of: a monitor(e.g., a cashier-facing monitor), one or more input devices (e.g.,scanners, keyboards, scales, or the like), one or more payment devices(e.g., cash drawers, card readers, etc.) for receiving or returningpayments, and one or more output devices (e.g., customer-facing displayor monitor, receipt printer, etc.).

Communication module 613 can be a wireless network adapter forconnecting POS system 611 with a local wireless network, such as, forexample, using Bluetooth and/or Wi-Fi. NFC module 604 is configured toconnect mobile device 601 with other systems and devices using NearField Communication.

FIG. 7 illustrates a flow chart of an example method 700 fortransferring digital receipt data to mobile devices. Method 700 will bedescribed with respect to the components and data of computerarchitecture 600.

Method 700 includes opening a sales transaction associated with a mobiledevice (701). A user of mobile device 601 can make one or more itemsthey wish to purchase available to a cashier. The cashier can thenprocess (e.g., scan) each of the items as part of a checkout procedure.Alternately, the user of mobile device 601 can process (e.g., scan) eachof the one or more items himself or herself as part of a self-checkoutprocedure. As part of the checkout process, a cashier or the user ofmobile device 601 can enter commands at I/O peripherals 616 to open anew sales transaction. In response, I/O peripherals 616 can send opentransaction message 632 to transaction processor 612. Transactionprocessor 612 can receive open transaction message 632 from I/Operipherals 616. In response to open transaction message 632,transaction processor 612 can open a sales transaction to process theone or more items for the user of mobile device 601.

Method 700 includes, in response to opening the sales transaction,collecting digital receipt data for the sales transaction (702). Forexample, in response to opening the sales transaction, transactionprocessor 612 can collect digital receipt data 633 for each of the oneor more items that is processed (e.g., scanned) during the salestransaction.

Method 700 includes transmitting a Near Field Communication (NFC) tagpayload within a generated Radio Frequency (RF) field surrounding themobile device, the tag payload encoding a unique customer identifier,the unique customer identifier corresponding to a receipt managementapplication resident at the mobile device (703). For example, NFC module604 can access application ID 631 from receipt management application602. NFC module 604 can transmit NFC tag payload 638 within a RF fieldrange of POS system 611. NFC tag payload 638 encodes application ID 631,a unique ID for receipt management application 602.

Method 700 includes receiving the Near Field Communication (NFC) tagpayload from the mobile device (704). For example, NFC module 614 canreceive NFC tag payload 638 from NFC module 604. NFC module 614 candecode application ID 631 from NFC tag payload 638 and send applicationID 631 to transaction processor 612.

Method 700 includes establishing a communication pairing between thepoint-of-sale (POS) system and the mobile device upon acceptance of theunique customer identifier (705). Method 700 includes establishing thecommunication pairing between the mobile device and the point-of-sale(POS) system, establishment of the communication pairing indicative ofthe point-of-sale (POS) system accepting the unique customer identifier(706). For example, upon POS system 611 accepting application ID 631from mobile device 601, mobile device 601 and POS system 611 canestablish communication pairing 652.

In some embodiments, communication pairing 652 is an NFC peer-to-peerdata connection. For example, NFC module 604 and NFC module 614 canestablish an NFC peer-to-peer data connection between mobile device 601and POS system 611. In other embodiments, communication pairing 652 is adifferent longer range wireless communication protocol pairing, such as,Bluetooth or Wi-Fi. For example, based on provided functionality,communication module 603 and communication module 613 can establish aBluetooth or a Wi-Fi connection between mobile device 601 and POS system611.

Method 700 includes closing the sales transaction at the point-of-sale(POS) system (707). For example, when each of the one or more items hasbeen processed (e.g., scanned), a cashier or the user of mobile device601 can enter commands at I/O peripherals 616 to end the salestransaction. In response, I/O peripherals 616 can send close transactionmessage 634 to transaction processor 612. Transaction processor 612 canreceive close transaction message 634 from I/O peripherals 616. Inresponse to close transaction message 634, transaction processor 612 canclose the sales transaction processing the one or more items for theuser of mobile device 601.

Method 700 includes in response to closing the sales transaction,sending the collected digital receipt data to the mobile device over theestablished communication pairing (708). For example, in response toclosing the sales transaction, POS system 611 can send digital receiptdata 633 to mobile device 601 over communication pairing 652. Whencommunication pairing 652 is a NFC peer-to-peer data connection, NFCmodule 614 can send digital receipt data 633 to NFC module 604. Whencommunications pairing 652 is a Bluetooth or a Wi-Fi connection,communication module 613 can send digital receipt data 633 tocommunication module 603.

Method 700 includes receiving the collected digital receipt data for thesales transaction from the Point-Of-Sale (POS) system over thecommunication pairing (709). For example, mobile device 601 can receivedigital receipt data 633 from POS system 611 over communication pairing652. When communication pairing 652 is a NFC peer-to-peer dataconnection, NFC module 604 can receive digital receipt data 633 from NFCmodule 614. When communications pairing 652 is a Bluetooth or a Wi-Ficonnection, communication module 603 can receive digital receipt data633 from communication module 613.

Establishing a communication pairing for a different longer rangewireless communication protocol can allow a user of mobile device 601 tomove mobile device 601 further away from POS system 601 physically andstill receive digital receipt data 633. For example, mobile device 601can function as an NFC tag. POS system 611 can function as an NFCreader. Mobile device 601 can be moved within a sufficient proximity ofPOS system 611 so that POS system 611 can receive NFC tag payload 638.After NFC tag payload 638 is received, the user may desire to put mobiledevice 601 back in a pocket, purse, etc. NFC communication can be usedto bootstrap a Bluetooth or Wi-Fi connection. Establishing communicationpairing 652 as a Bluetooth or Wi-Fi connection can permit the user to“put away” a mobile device and remain within communication range of POSsystem 611.

Method 700 includes delivering the collected digital receipt data to thereceipt management application (710). For example, as appropriate, NFCmodule 604 or communication module 603 can deliver digital receipt data633 to receipt management application 602. Receipt managementapplication 602 can then process digital receipt data 633 to sortdigital receipt data 633, search digital receipt data 633, itemizedigital receipt data 633, etc. in response to user-entered commands.

FIG. 8 illustrates an example schematic block diagram of a point-of-sale(POS) system 800. In some embodiments, the hardware, software, orhardware and software of POS system 800 may be configured to implementone or more methods in accordance with the present invention. Forexample, POS system 800 may be manufactured, programmed, modified, orupgraded to support transferring digital receipt data to mobile devices.Any of POS systems 211, 411, and 611 can be a POS system similar to POSsystem 800.

POS system 800 can include various components. In some embodiments, POSsystem 800 includes a central or primary computer 812, a monitor 814(e.g., a cashier-facing monitor 814), one or more input devices 816(e.g., scanners 816 a, keyboards 816 b, scales, or the like), one ormore payment devices 818 (e.g., cash drawers 818 a, card readers 818 b)for receiving or returning payments, one or more output devices 820(e.g., customer-facing display 820 a or monitor 820 a, receipt printer820 b), or the like or combinations or sub-combinations thereof, and NFCmodule 822, such as, for example, an NFC dongle.

Computer 812 may form the backbone of POS system 800. Other components816, 818, 820, 822 forming part of a POS system 800 can communicate withcomputer 812. Input devices 816 and certain payment devices 818 can feeddata and commands to computer 812 for processing or implementation. Forexample, scanner 816 a can pass data communicating the identity of oneor more items to be purchased, returned, or the like to a computer 812.Similarly, card reader 818 b can pass payment information to computer812.

On the other hand, output devices 820 and certain payment devices 818can follow or implement commands issued by computer 812. For example,cash drawer 818 a may open in accordance with the commands of computer812. Similarly, customer-facing display 820 a and receipt printer 820 bcan display or output data or information as instructed by computer 812.

In some embodiments, in addition to handling consumer transactions(e.g., purchases, returns), POS system 800 can provide or supportcertain “back office” functionality. For example, POS system 800 canprovide or support inventory control, purchasing, receiving andtransferring products, or the like. POS system 800 can also store salesand customer information for reporting purposes, marketing purposes,receivables management, trend analysis, cost analysis, price analysis,profit analysis, or the like. If desired or necessary, POS system 800can include an accounting interface to pass certain information to oneor more in-house or independent accounting applications.

In some embodiments, POS system 800 operates substantiallyindependently, as a stand-alone unit. Alternately, POS system 800 may beone of several POS systems 800 forming the front line of a largersystem. FIG. 9 illustrates an example schematic block diagram of anetwork 900 of point-of-sale (POS) systems 800. For example, multiplePOS systems 800 may operate at a particular location 922 (e.g., within aretail, brick-and-mortar store). In such embodiments, the various POSsystems 800 may be interconnected via LAN 924. LAN 924 may also connectthe POS systems 800 to a local server 926.

Local server 926 can support the operation of the associated POS systems800. For example, a server 926 may provide a central repository fromwhich certain data needed by the associated POS systems 800 may bestored, indexed, accessed, or the like. Server 926 can serve certainsoftware to one or more POS systems 800. In certain embodiments, a POSsystem 800 can offload certain tasks, computations, verifications, orthe like to server 926.

Alternatively, or in addition thereto, server 926 can support certainback office functionality. For example, server 926 can receive andcompile (e.g., within an associated database 928) data from the variousassociated POS systems 800 to provide or support inventory control,purchasing, receiving and transferring products, or the like. Server 926can also receive and compile sales and customer information forreporting purposes, marketing purposes, receivables management, trendanalysis, cost analysis, price analysis, profit analysis, or the like.

In some embodiments, one or more POS systems 800 and/or servers 926corresponding to a particular location 922 can communicate with oraccess one or more remote computers or resources via one or more networkdevices 930. For example, a network device 930 can enable a POS system800 to contact outside resources and verify the payment credentials(e.g., credit card information) provided by a customer. A network device930 can comprise a modem, router, or the like.

In selected embodiments, POS systems 800 operate within anenterprise-wide system 931 comprising multiple locations 922 (e.g.,branches 922 or stores 922). In such embodiments, each location 922 mayhave one or more POS systems 800, local servers 926, local databases928, network devices 930, or the like or combinations orsub-combinations thereof connected by a computer network (e.g., a LAN924). It may be that any of data receipt servers 221, 421, and 621 areincluded in and/or include the functionality of a local server 926.

Additionally, each such location 922 may be configured to interact withone or more supervisory systems 932. For example, multiple branchlocations 922 may report to an associated “headquarters” location orsystem. It may be that any of data receipt servers 221, 421, and 621 areincluded in and/or include the functionality of a supervisory system932.

A supervisory system 932 can include one or more supervisory servers934, databases 936, workstations 938, network devices 940, or the likeor combinations or sub-combinations thereof. The various components of asupervisory system 932 can be interconnected via a computer network(e.g., a LAN 942). In selected embodiments, a supervisory system 932includes one or more supervisory servers 934 providing a centralrepository from which certain data needed by the one or more POS systems800 or local servers 926 may be stored, indexed, accessed, or the like.

Alternatively, or in addition thereto, a supervisory server 934 canreceive and compile (e.g., within an associated database 936) data fromthe various associated POS systems 800 or local servers 926 to provideor support inventory control, purchasing, receiving and transferringproducts, or the like. A supervisory server 934 may also receive andcompile sales and customer information for reporting purposes, marketingpurposes, receivables management, trend analysis, cost analysis, priceanalysis, profit analysis, or the like.

A supervisory system 932 can be connected to one or more associatedlocations 922 or branches 922 in via any suitable computer network 944(e.g., WAN 944). For example, in selected embodiments, one or morelocations 922 can connect to a supervisor system 932 via the Internet.Communication over such a network 944 can follow any suitable protocolor security scheme. For example, communication may utilize the FileTransfer Protocol (FTP), a virtual private network (VPN), intranet, orthe like.

Although the components and modules illustrated herein are shown anddescribed in a particular arrangement, the arrangement of components andmodules may be altered to process data in a different manner. In otherembodiments, one or more additional components or modules may be addedto the described systems, and one or more components or modules may beremoved from the described systems. Alternate embodiments may combinetwo or more of the described components or modules into a singlecomponent or module.

The foregoing description has been presented for the purposes ofillustration and description. It is not intended to be exhaustive or tolimit the invention to the precise form disclosed. Many modificationsand variations are possible in light of the above teaching. Further, itshould be noted that any or all of the aforementioned alternateembodiments may be used in any combination desired to form additionalhybrid embodiments of the invention.

Further, although specific embodiments of the invention have beendescribed and illustrated, the invention is not to be limited to thespecific forms or arrangements of parts so described and illustrated.The scope of the invention is to be defined by the claims appendedhereto, any future claims submitted here and in different applications,and their equivalents.

What is claimed:
 1. A method for enabling the transfer of digitalreceipt data from a Point-Of-Sale (POS) computer system to a mobiledevice, the Point-Of-Sale (POS) computer system including one or moreprocessors and system memory, the Point-Of-Sale (POS) computer systemalso including a Near Field Communication (NFC) module, the methodcomprising: opening a sales transaction at the Point-Of-Sale (POS)computer system; in response to opening the sales transaction,collecting digital receipt data for the sales transaction; one or moreprocessors of the POS computer system executing the Near FieldCommunication (NFC) module to receive a Near Field Communication (NFC)tag payload from the mobile device within range of a generated RadioFrequency (RF) field, the Near Field Communication (NFC) tag payloadencoding an application ID associated with and unique to a receiptmanagement application resident at the mobile device; closing the salestransaction at the Point-Of-Sale (POS) computer system; and employingthe application ID associated with the receipt management application tolink the digital receipt data to the mobile device, the employingcomprising: using the application ID associated with the receiptmanagement application to mark the digital receipt data for the salestransaction as corresponding to the receipt management application; andsending the marked digital receipt data for the sales transaction to areceipt data server for subsequent retrieval by the mobile device. 2.The method of claim 1, further comprising sending a push notification tothe mobile device, the push notification indicating that digital receiptdata for the sales transaction is available for retrieval from thereceipt data server.
 3. The method of claim 1, wherein the opening thesales transaction at the Point-Of-Sale (POS) computer system comprisesreceiving an indication from an I/O peripheral that the salestransaction is to be opened.
 4. The method of claim 1, wherein thecollecting the digital receipt data for the sales transaction, comprisesfor each of one or more items included in the sales transaction:receiving an item identifier from a scanned bar code; and referring to aproduct database to access item description data and item cost data forthe item.
 5. The method of claim 1, wherein the closing the salestransaction at the Point-Of-Sale (POS) computer system comprisesreceiving an indication from an I/O peripheral that the salestransaction is to be closed.
 6. The method of claim 1, wherein thesending the marked digital receipt data for the sales transaction to thereceipt data server comprises sending the marked detail receipt data toa local server that stores receipt data for the Point-Of-Sale (POS)system along with one or more other Point-Of-Sale (POS) systemsco-located with the Point-Of-Sale (POS) system.
 7. The method of claim1, wherein the sending the marked digital receipt data for the salestransaction to the receipt data server comprises sending the markeddetail receipt data to a supervisory system that stores receipt data fora location of the Point-Of-Sale (POS) system and for one or more otherlocations of Point-Of-Sale (POS) systems.
 8. A method for a mobiledevice to receive digital receipt data from a Point-Of-Sale (POS)system, the mobile device including one or more processors and systemmemory, the mobile device also including a Near Field Communication(NFC) module, the method comprising: one or more processors of themobile device executing the Near Field Communication (NFC) module totransmit a Near Field Communication (NFC) tag payload to thePoint-Of-Sale (POS) system within a Radio Frequency (RF) field range ofthe Point-Of-Sale (POS) system, the Point-Of-Sale (POS) system handlinga sales transaction associated with the mobile device, the Near FieldCommunication (NFC) tag payload encoding an application ID associatedwith and unique to a receipt management application resident at themobile device; receiving a push notification, the push notificationnotifying the mobile device that digital receipt data for the salestransaction is available at a receipt data server, wherein receipt ofthe push notification is indicative of the Point-Of-Sale (POS) systemhaving received the Near Field Communication (NFC) tag payload andaccepted the application ID associated with the receipt managementapplication; requesting digital receipt data corresponding to theapplication ID associated with the receipt management application fromthe receipt data server; and receiving, by the receipt managementapplication, the digital receipt data for the sales transaction from thereceipt data server in response to the request.
 9. The method of claim8, further comprising: the Near Field Communication (NFC) moduleaccessing the application ID associated with the receipt managementapplication from the receipt management application; and the Near FieldCommunication (NFC) module encoding the application ID associated withthe receipt management application into the Near Field Communication(NFC) tag payload.
 10. The method of claim 8, wherein the requesting thedigital receipt data from the receipt data server comprises requestingthe digital receipt data from a local server that stores receipt datafor the Point-Of-Sale (POS) system along with one or more otherPoint-Of-Sale (POS) systems co-located with the Point-Of-Sale (POS)system.
 11. The method of claim 10, wherein the receiving the digitalreceipt data for the sales transaction from the receipt data servercomprises receiving the digital receipt data for the sales transactionfrom the local server.
 12. The method of claim 8, wherein the requestingthe digital receipt data from the receipt data server comprisesrequesting the digital receipt data from a supervisory system thatstores receipt data for a location of the Point-Of-Sale (POS) system andfor one or more other locations of Point-Of-Sale (POS) systems.
 13. Themethod of claim 12, wherein the receiving the digital receipt data forthe sales transaction from the receipt data server comprises receivingthe digital receipt data for the sales transaction from the supervisorysystem.
 14. A method for enabling the transfer of receipt data from acomputer system corresponding to a retailer to a mobile devicecorresponding to a customer, the method comprising: initiating, by aprocessor of a point-of-sale (POS) terminal, a sales transaction, thePOS terminal being a part of the computer system corresponding to theretailer; collecting, by the POS terminal, the receipt data for thesales transaction; receiving, by a near-field-communication (NFC) moduleof the POS terminal, an NFC payload from the mobile device, the NFCpayload encoding an application ID associated with and unique to areceipt management application resident at the mobile device;completing, by the POS terminal, the sales transaction; and using, bythe computer system corresponding to the retailer, the application IDassociated with the receipt management application to send a pushnotification to the mobile device, the push notification indicating thatdigital receipt data for the sales transaction is available forretrieval.